-
-
Notifications
You must be signed in to change notification settings - Fork 196
feat: outgoing traceparent header support
#1394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@sentry review |
|
@sentry review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that looks great; only minor things.
What I currently miss is a user-facing explanation of the hierarchy between sentry-trace and traceparent on the incoming side (which is unaffected by propagate_traceparent). That's totally fine if it's evident in the accompanying docs.
Also, does this currently test an outgoing traceparent coexisting with a sentry-trace (they are not mutually exclusive when outgoing, right)?
| bool attach_screenshot; | ||
| bool crashpad_wait_for_upload; | ||
| bool enable_logging_when_crashed; | ||
| bool propagate_traceparent; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One of these days, we should convert all these flags to bitfields. But not in this PR.
Co-authored-by: Mischan Toosarani-Hausberger <[email protected]>
Co-authored-by: Mischan Toosarani-Hausberger <[email protected]>
Co-authored-by: Mischan Toosarani-Hausberger <[email protected]>
Co-authored-by: Mischan Toosarani-Hausberger <[email protected]>
* cleanup * remove feature of parsing incoming traceparent * re-add len macros
…for transactions and spans
traceparent header supporttraceparent header support
|
Vercel previews: - [options](https://sentry-docs-git-joshua-featpropagatetraceparentoption.sentry.dev/platforms/native/configuration/options/#propagate-traceparent) - [trace propagation example](https://sentry-docs-git-joshua-featpropagatetraceparentoption.sentry.dev/platforms/native/tracing/trace-propagation/custom-instrumentation/) ## DESCRIBE YOUR PR Documents the changes from getsentry/sentry-native#1394 ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
Fixes #1350
For now, this is only propagated on outgoing requests. The handling of incoming requests was initially added too (see commit range), but this is not required (yet) by our spec.
Related docs PR getsentry/sentry-docs#15162
Develop Docs:
propagatetraceparent
w3c-trace-context-header